You can access Qlik Sense demo apps from https://demos.qlik.com/.

If you are looking for real-life business examples, our Qlik Gallery hosts a platform meant for sharing apps, outcomes, and ideas. It is not restricted to Qlik-provided demos and mostly consists of customer examples.

If you are looking to download demo apps:

1. Go to https://demos.qlik.com/ 
2. Select Downloadable from the available Tags
   
3. Open the App
4. A Download button will be available (if logged in)
   
   

It is not possible to set up a Microsoft Office 365 email provider with OAuth 2.0 authentication.
The HAR file shows this message in Network:

{connectionFailed: true, message: "Error during email request", success: false}
connectionFailed: true
message: "Error during email request"
success: false

Resolution

Configure the Mail.Send permission as it is described in Configuring a Microsoft 365 email provider using OAuth2.

Cause

This problem occurs when the Mail.Send permission has not been configured in the app registration.

Related Content

More information about the  Mail.Send permission can be found in Application permission to Microsoft Graph (learn.microsoft.com).

Environment

• Qlik Tabular reporting
• Qlik Cloud

When embedding a sheet in an iFrame, the "full screen" toggle button for Qlik Sense native chart objects is missing. This feature is present at the sheet level in the hub

Full Screen toggle button is available at the sheet level in the hub

The same feature is  missing, once a sheet is added in an iFrame (Single Configurator)

Environment

• Qlik Sense Enterprise (all versions)

Resolution

This is a known limitation.

An improvement task has been created (Jira task VIZ-103) and an idea is available on our Ideation Platform.

To check the current status or to add your vote, head over to the idea: full screen for iframe and embed 

Internal Investigation ID(s):

QB-4967
VIZ-103

When changing the name of a dataset, the source name still stays the same. This can be seen by uploading a  “firstname.qvd" and renaming it to “secondname.qvd”. 

The dataset's detail will show "firstname.qvd" as the source.

As a consequence:

1. you can have several datasets with the same name, but different sourcenames.
2. the data load editor always refers to the source name (“firstname”), not the data set name. 
   
   
   

   
   Trying to load  “FROM [lib://DataFiles/secondname.qvd]” will produce a "(Connector error: File not found)" error.

Resolution

This is not a defect, it's how the product is designed.

A dataset represents a data resource with its properties such as name. The value of that is that you are able to use more user-friendly names of datasets without having to change the source names, which can be useful when the dataset is pointing to a database table for instance.

In the future, there is a plan to add the possibility of calling the name of the datasets in the script. 

Environment

Qlik Cloud 

Scripts need to be exported using the Qlik Sense Engine APIs.

Resolution

The Engine API and the Capability API both have a method/function called GetScript() that will allow the app script to be exported. Once the script is accessed, it can be saved to disc, for example, a folder that is perhaps monitored by a change control system. The Engine API can be found here and the Capability API can be found here. The following are examples of both APIs:

Engine API:

IAppIdentifier foundAppIdentifier = _location.AppWithId("....appId....");
IApp app = _location.App(foundAppIdentifier);
string script = app.GetScript();
Console.WriteLine(script);

Capability API:

var app = qlik.openApp("....appId....");
app.getScript().then( function(script){
  console.log(script);
});

Related Content:

Get started with APIs on Windows 
GetScript Method (Engine)
getScript method (Capability API)

Qlik Sense: call Qlik Sense Engine API with Python 
Qlik Sense Repository API/Engine API(Enigma.js) example with JWT authentication: duplicate/scramble/export 
Qlik Sense: Getting started with the .NET SDK 

When using Qlik REST connector to load data from API sources that return JSON or XML response, sometimes a huge data model with many tables is returned although the response contains only a single table.
For example, the following JSON message is parsed into 5 single-row tables instead of one table with 5 rows:

Environment:

• Qlik REST connector 2.11.0 (default connector in Qlik Sense April 2019)

Cause:

The JSON response has a "nested" structure, i.e each data record is stored as a separated JSON object, which is not member of an array.

Qlik REST connector applies a standard strategy for parsing JSON response:

• Each stand-alone object {..} (not being element of an array) is parsed as a new table
• Each array [..] is parsed as a new table. If the array contains multiple objects, each object will take one line in the resulting table

As a result, nested JSON response is parsed as multiple tables instead of a single flat table. You can find the same strategy in other JSON parsing tool, such as http://json2table.com/.

The same logic applies to nested XML responses.

Resolution:

Qlik REST connector does not yet support loading JSON/ XML responses with nested structure. There is an ongoing improvement request to support this structure in future releases of the connector.
Meanwhile, please consider the following work-around solution:

• For XML: Use a WebFile connection to load the response instead of REST connector. WebFile connection supports reading XML with [XmlSimple, table is...] instruction, which works with nested XML tables. Check the following community discussion for more details: https://community.qlik.com/t5/Qlik-Sense-Data-Connectivity/Can-I-query-nested-XML-data-over-REST-such-that-I-get-a-flat/td-p/1568751
• For both:
  • Develop an external script (such as Python) to download, parse the JSON/ XML response and store the flat table into a local data file. Use EXECUTE command to trigger the external script from Qlik and load data from the file.
  • If you have access to modify the API source, adjust the response format so that each record is stored as a member object of an array. For instance, the example above can be adjusted as follows:

QlikView and Qlik Sense files are like ZIP file, as in they are highly compressed. So obtaining an estimate of how much RAM is needed for loading Apps into memory (footprint) is difficult to provide across the board. The expected memory usage associated with the app can also depend on how many users access the app and how much they are used.

Environment: 

• QlikView, all versions
• Qlik Sense Enterprise on Windows,  all versions
• Qlik Cloud

An estimate of the RAM needed per app can be built on the below, but for accuracy always test by loading the app into memory and using the Qlik Scalability Tools to obtain a baseline of memory usage for each app as it is accessed by the foreseeable number of users. 

Telemetry logging which allows for using the Telemetry Dashboard, is also an available suitable tool.

Since the release of the February 2019 version, Sense System Performance Analyzer monitoring App can be used to determine app footprint as well. Since the release of the June 2018 version, App Metadata Analyzer monitoring App can also be used. However, these last three may not provide the same data as the Scalability Tools.

An alternative is to use a test environment and simply observe RAM usage increases as apps are first opened (footprint), and as number of users accessing the app increase, then as number of operations are performed within the app. The test environment results for observed memory and CPU usage can be recorded as a baseline for the particular app in production, which assists in determining future sizing/scaling needs.

Need direct assistance in evaluating your Qlik Sense and QlikView apps? Qlik's Professional Services are available to assist you.

RAMInitial = SizeOnDisk × FileSizeMultiplier ; this is the initial RAM footprint for any application 

FileSizeMultiplier: range between 2-10 (this is a compression* ratio depending on the data contained in the app) 

*Compression is based upon the data, and how much we can compress depends upon the homogeneity of the data. The more homogeneous, the more compression Qlik can achieve. 
More information on one way of optimizing a document can be found on the Qlik Design Blog: Symbol Tables and Bit-Stuffed Pointers

RAMperUser = RAMinitial ×  userRAMratio ; this is the RAM per each incremental user 

userRAMratio: range between 1% -10%
 

Total RAM used per app :

TotalRAM = (RAMperUser × Number of users) + RAMinitial 

Example:

SizeOnDisk = 1 GB

File Size Multiplier 6 (range is from 2 to 10) This is an example value. A value can be obtained by reviewing telemetry (how far does the app expand?) or opening the app in a QlikView or Qlik Sense desktop and measuring the expansion based on how large it grows in memory.

RAMinitial = 1 * 6 = 6 GB

If we take a RAM Ratio per User of 6% then it is 0.06 (range is from 1 to 10)

RAMperUser = 6 x 0.06 = 0.36GB

Then RAM Required for 30 Users

TotalRAM = (RAMperUser × No. users) + RAMinitial 
TotalRAM =  (0.36 * 30) + 6
TotalRAM = 16.8 GB

Related Content:

• App Metadata Analyzer
• Sense System Performance Analyzer 
• Qlik Sense Scalability Tools - Community
• How to enable Qlik Sense QIX performance logging and use the Telemetry Dashboard
• Single/Multi-threading in QlikView
• Qlik Sense Performance Benchmark
• Qlik Sense Scalability Tools

This Support Techspert Thursday session addresses:
- Difference between SaaS and Windows
- Different kinds of Alerts
- Troubleshooting tips

00:00 - Intro

01:00 - What is Qlik Alerting?

01:36 - How Alerting Works

02:58 - Licenses Capabilities

03:38 - Different Types of Alerts

05:13 - Enabling Alerting in Qlik Sense SaaS

05:49 - Creating Alerts in SaaS

07:32 - Setting up Qlik Alerting Button on Windows

08:33 - Fixing Certification error

10:00 - Creating Alertis on Windows

12:06 - Customized Notifications

13:23 - Syncing Users with Qlik Sense

14:01 - Changing Qlik Alerting Ports

15:59 - Using Dev Hub to change ports

17:15 - How to Troubleshoot Errors

18:23 - Searching for more info

19:01 - Creating System Alerts

19:53 - Alerting Log Files

21:12 - Setting up Monitoring App

23:50 - Documentation on Help.Qlik.Com

24:40 - Q & A

Resources:

STT - Troubleshooting Qlik Alerting Setup

Qlik Alerting Documentation

Custom Notifications

Articles on Support Knowledge Base

Q&A:

Q: Can we make App specific Data Job alerts (Success/Failure)? 

A: Yes, if you would like to get an alert when a specific app has been reloaded successfully or otherwise has failed, then you can use “System alerts” 

Q: From which Qliksense version onwards alerts are available?

A: According to the help page: Minimum recommended version of Qlik Sense Enterprise on Windows is February 2019. 

Q: How can I get an alert if a QlikView job fails to load, or if an NPrinting job fails to execute? 

A: Not possible, for now Qlik Alerting is only available to set it up with Qlik Sense, starting from QS February 2019 .

Q: Hello, I have a questions regarding the conditions. They seemed to only use operators, but can we apply filters or selections to the alert? 

A: Yes, you can apply filters and conditions.

Q: In DATA alert, can you edit an ADDED MEASURE?

A: If you mean if you can edit a measure once it has been created, yes you can do it after from the QA web console.

Q: Is it mandatory to have different machines for Qlik Sense and Qlik Alerting? 

A: Not mandatory but best practice is to have them in separate machines.

Q: Can you loop through Selections to test condition on each?

A: Yes, using filters and more advanced conditions, you can find some examples in our Help Page.

Q: Since it's included in SaaS, does that mean there's no added cost? 

A: Yes, exactly, for Qlik Sense Enterprise SaaS there is no extra cost, but it is only available for SaaS Enterprise, not in Qlik Sense Business. 

Q: Can Custom notifications be used to send alerts in another language?

A: Yes, sure, it can be sent in any language as they are custom notification so you only need to put whatever text you like. 

Transcript:

Qlik ODBC connector package (database connector built-in Qlik Sense) fails to reload with error Connector reply error:

Executing non-SELECT queries is disabled. Please contact your system administrator to enable it.

The issue is observed when the query following SQL keyword is not SELECT, but another statement like INSERT, UPDATE, WITH .. AS or stored procedure call.

Environment:

• Qlik Sense Enterprise on Windows
• Qlik Sense Desktop
• QlikView Server
• QlikView Desktop

Cause

See the Qlik Sense February 2019 Release Notes for details on item QVXODBC-1406.

Resolution

By default, non-SELECT queries are disabled in the Qlik ODBC Connector Package and users will get an error message indicating this if the query is present in the load script. In order to enable non-SELECT queries, allow-nonselect-queries setting should be set to True by the Qlik administrator. 


To enable non-SELECT queries:

1. Modify the QvOdbcConnectorPackage.exe.config found in the locations mentioned below.
   Set the parameter allow-nonselect-queries to True  
   
   This is case-sensitive. true will not work.
   
   In a multi node environment, the changes need to be applied to all nodes.
   Configuration file QvOdbcConnectorPackage.exe.config locations:
   
   
   • Qlik Sense Enterprise: C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage
   • Qlik Sense Desktop: C:\Users\user-name\AppData\Local\Programs\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage
   • QlikView: C:\Program Files\Common Files\QlikTech\Custom Data\QvOdbcConnectorPackage
     

     As we are modifying the configuration files, these files will be overwritten during an upgrade and will need to be made again.

     
     
     
2. Non-select statements are now enabled and generally this is sufficient to resolve the issue.
   
   If, however, you need to run SQL statements without any data table returned (INSERT/ UPDATE/ DELETE/ DROP), you can optionally add the keyword !EXECUTE_NON_SELECT_QUERY at the end of the query. Other queries that return data (such as WITH ... AS in PostgreSQL) do not need this keyword.
   
   The EXECUTE_NON_SELECT_QUERY signals to the script processing engine that the query may not return any data.
   

   Only apply !EXECUTE_NON_SELECT_QUERY if you use the default connector settings (such as bulk reader enabled and reading strategy "connector"). Applying !EXECUTE_NON_SELECT_QUERY to non-default settings may lead to unexpected reload results and/or error messages.

More details are documented in the Qlik ODBC Connector package help site.

Related Content:

Feature Request Delivered: Executing non-SELECT queries with Qlik Sense Business 
Execute SQL Set statements or Non Select Queries

QlikView and Qlik Sense load either missing or additional zeros, compared to the values in the data source. 

For example data like in the below script is loaded with incorrect leading zeros. 

LOAD * Inline [
F1, F2
1, a
01, b
02, c
2, d
];

On the second row the leading zero is missing, and on the fourth row, there is an unexpected additional leading zero.

Environment:

QlikView 
Qlik Sense Enterprise on Windows 
Qlik Cloud 

Cause:

The observed behaviour is a part of fundamental Qlik engine functionality and data compression technique. 

In short, this means that Qlik interprets and associates loaded data by best effort. As part of Qlik optimization and compression technique the same reoccurring value in a field is stored on the first occurrence only, and the following occurrence reference to the first (stored) value. This means that two values with identical numerical representation can not be stored with two different textual presentations in the same field in Qlik.

Please keep in mind that all numerical values in Qlik act as dual values. This means that they have an underlying numerical value that is used for calculations, and a textual formatted value which is the value seen in charts or as calculations results. 

In the example below four rows of data are loaded. In the field F1 there are four different value.

LOAD * Inline [
F1, F2
1, a
01, b
02, c
2, d
];

1. The first value in F1 is interpreted by Qlik as a numerical 1
2. The first value is stored as numerical value 1 with textual presentation 1
3. The second value in F1 is interpreted by Qlik as a numerical 1
4. There is already a numerical value 1 stored in the field F1, so Qlik associates the second occurrence to the first value. This means that the value 01 will be associated as a numerical 1 with presentation value 1.
5. The third value in F1 is interpreted by Qlik as a numerical 2
6. There is no other value stored in the field  F1 as a numerical 2, hence this value is stored as numerical 2 with the textual presentation value 02.
7. The fourth value in F1 is interpreted by Qlik as a numerical 2
8. There is already a numerical value 2 stored in the field F1, so Qlik associates the second occurrence to the first value. This means that the value 2 will be associated as a numerical 2 with presentation value 02.
9. The loaded data will visually not look like the data source. 
   
   
   

    

Resolution:

Identical numerical values are associated with the same textual presentation value in Qlik . For this reason, it is not possible to store the same numerical value with different textual presentation values. 

One way to resolve this is to format the values as text by using Text() during reload. 

LOAD 
    text(F1) as F1,
    F2
Inline [
F1, F2
1, a
01, b
02, c
2, d
];

This will result in the visual values looking identical to the data source. 

NOTE: Value formatted with Text() will not have underlying numerical values, hence calculations on these values is not possible. 

Publishing an app in a Qlik Sense Enterprise on Windows (client-managed) environment may fail with the error:

Quota is exceeded

Resolution

Reduce the size of files attached to the app. Alternatively, delete unnecessary files you have attached to it.

You can review what files you have attached to the app from the Qlik Sense Management Console:

1. Open the Qlik Sense Management Console in a supported browser
2. Go to Apps
3. Locate and highlight the app you cannot publish 
4. Click Edit
   
   
   
   
5. Open the App content menu tab on the right side of the screen; this will provide an overview of your attached files and how large they are. 
   
   You can now choose to review the files and reduce them in size, or:
6. Choose the file you wish to delete and click Delete
   
   

Cause

The maximum file size of an individual file attached to an app is 50 MB, while the maximum total size of files attached to the app (including image files uploaded to the media library) is 200 MB.

See Attaching data files and adding the data to the app for details.

Related Content

Attaching data files and adding the data to the app | Qlik Sense on Windows Help

Environment

• Qlik Sense Enterprise for Windows

Table of content: 

• Writeback use case
• Two ways to execute an automation from a Qlik Sense Sheet
• 1. Native 'execute automation' action in the Qlik button
• 2. Link a triggered automation from your Qlik Sense Sheet.
• Example 1: Open website or URL (button)
• Example 2: Add an action link in your straight table
• Example 2: Extension with input forms
• Additional Notes
• Demo application with automations

 

Writeback use case

Qlik Application Automation was released in Qlik Cloud on September 28th, 2021, and has helped many customers take action on their data and automated numerous operational day-to-day workflows.  

One of the key use cases we’ve seen in the first year is the writeback use case where users can, from a single click on a Qlik Sense dashboard, add, correct, or update data into their operational system (e.g. Salesforce, Jira, HubSpot, Service Now) or into the data platform (e.g. Snowflake, MySQL) used for the data load. 

On April 20th 2023 we released a new Qlik Sense Button that has improved functionality to trigger an automation - see https://community.qlik.com/t5/Official-Support-Articles/How-to-build-a-write-back-solution-with-native-Qlik-Sense/ta-p/2059047

Example Qlik Sense sheet using automations for writeback use cases (source: Alberto Vaghi - Solution Architect Qlik)

 

In this article, we want to share an overview of the current building blocks for writeback use cases that are natively available in Qlik Cloud by using the power of Qlik Application Automation.

Two ways to execute an automation from a Qlik Sense Sheet

In short, we have two mechanisms to execute an automation from a Qlik Sense Sheet. 

 

1. Native 'execute automation' action in the Qlik button

In the 'Actions' menu item from the native button, the option 'Execute automations' will link a button natively to an automation. More information on triggering an automation from the native Qlik Sense button can be found here: https://community.qlik.com/t5/Official-Support-Articles/How-to-build-a-write-back-solution-with-native-Qlik-Sense/ta-p/2059047 

 

Why choose this option?	Current Limitations
Native button No limitation on selection list (because we are using the bookmark)  Easy setup Access control (only private)	No parallel run execution Run queuing limit see limitation page

 

2. Link a triggered automation from your Qlik Sense Sheet. 

By making your automation triggered, you allow any system to connect to your automation. Inputs and data can be shared through the URL as query string params (get) or the body (post).

 

Example Automation that is triggered from a Qlik Sense Sheet with 2 inputs: (opportunity)Id and (opportunity)stage

 

In a Qlik Sense Sheet, you can link a triggered automation in a button by using the 'open website or email' option in the navigation section, or by adding the link in a straight table.  Details of these two options are shared below. 

 

Why choose this option?	Current Limitations
The button can be used by everyone that has access to the sheet Multiple records can be updated at once  The user can get feedback in the opened window or get redirected to another page	Opens new window No parallel run execution Run queuing limit see limitation page No access control on who can trigger

 

 

Example 1: Open website or URL (button)

 In this example, we have a list of opportunities that can be selected and assigned a new opportunity stage.

Example Qlik Sense Sheet with a button triggering an automation using the 'open website' option

 

The website URL configuration consists of :

1. The automation trigger URL
2. The input parameters added as query string params with the link to the selected items
3. Optional additional metadata parameters to be used for tracing purposes such as user or timestamp 

 Example:

https://<tenantname>/api/v1/automations/<automation_id>/actions/execute?X-Execution-Token=<token>&stage=' & GetFieldSelections([Stage Enum]) & '&opportunity_id=' & GetFieldSelections(Id) & '&user=' & SubField(OSUser(), '=', -1)

 

Example 2: Add an action link in your straight table

The same approach can be used as in Example 1, where we now configure the trigger URL as a column for each action option. The user will only be able to update one record at a time but does not need to make any selection upfront.  

Example of a Qlik Sense Straight table that triggers in the last 3 columns an automation to compel action

 

The configuration steps for the additional columns are:

1. Add per action option (in this case 'opportunity stage') a new column in the section 'data'.
2. Configure the triggered automation URL in that specific column using the data from another column (in this case 'opportunity id'), hardcoded action option (in this case 'opportunity stage'), and optionally some metadata for tracing purposes.
3. Set representation option to 'link' and set options 'link setting' = add label, 'link label' =open.

Example:

https://<tenantname>/api/v1/automations/<automation_id>/actions/execute?X-Execution-Token=<token>&stage=Open'& '&opportunity_id=' & [Id] & '&user=' & SubField(OSUser(), '=', -1)

 

Column configuration

 

 

Example 2: Extension with input forms

There are extensions available leveraging the same underlying principles and providing the user with an easy-to-use input form. An example is a great extension built by the Qlik principle solution architect Riley MacDonald: https://github.com/rileymd88/automation-trigger

Example of input form using the extension

 

 

Additional Notes

• In many cases, the app will need to be reloaded when the source data is updated by the writeback. It is advisable not to reload the application from within a triggered automation, such as is done in the attached demo examples. A triggered automation that includes an application reload may fail when there are multiple users interacting with the application since parallel reloads of the same app are not possible.

  We suggest using a separate automation to execute the reloads. This automation should be configured to run on a schedule. By doing this, the reloads can be scheduled at intervals and will pool multiple changes from writing back in the same reload. Database connectors and some other connectors have incremental blocks which allow you to only process new or updated records. Use these blocks in the automation to only perform a reload if any new or updated records were found.

  

   

• When using the triggered automation option, the system will open a new tab or window when clicking the button. You can configure the automation to:
  • Provide feedback to the users by using the 'output' block
  • Redirect the user to a specific page such as the opportunity record in the source system by using the 'redirect' block
  • Autoclose the tab by using the redirect block to a website that autocloses

Example using the output block

Example using the redirect block

 

• Using variables to provide feedback to the user can also be used. However, there might be challenges keeping the two sessions in sync - see this article.
• It is advised to keep track of the changes in a separate database or store them with metadata such as the changelog, user, and timestamp. 
• Many Qlik Partners provide more advanced solutions for writeback. This article focuses on the out-of-the-box features supporting basic use cases. 

 

Demo application with automations

Attached you will find a Zip file containing a demo application that shows different examples of how writeback can be implemented. Besides the application and the automations you will also find the required MySQL table data in CSV format for import. 

Configuration of MySQL

1. Import table writeback_source.
2. Import table writeback_changes.

Configuration of load script sections in this application

1. "Main" - Add MySQL connection.
2. "Original Data" - Configure to read from MySQL table writeback_source.
3. "Changelog" - Configure to read from MySQL table writeback_changes.
4. "Merged Data" - Configure writeback_source & writeback_changes.

Configuration of the automation

Triggered automation - Open a website or email.

Required block configurations:

1. "Do Query" - Add MySQL connection.
2. "Update Variable" - Use "do lookup" to configure App Id (Writeback demos) & Variable Id (last_update).
3. "Do Reload" - Use "do lookup" to configure App Id (Writeback demos).
4. "Save App" - Writeback demos.

Triggered automation - Extension

Required block configurations:

1. "Do Query" - Add MySQL connection.
2. "Update Variable" - Use "do lookup" to configure App Id (Writeback demos) & Variable Id (last_update).
3. "Do Reload" - Use "do lookup" to configure App Id (Writeback demos).
4. "Save App" - Writeback demos.

Execute automation - Native button

Required block configurations:

1. "Get Straight Table Data" - Use "do lookup" to configure App Id (Writeback demos), Sheet Id (Execute automation - Native button) & Object Id (the Id of the straight table: "Multiple selections of Ids allowed").
2. "Get Straight Table Data 2" - Use "do lookup" to configure App Id (Writeback demos), Sheet Id (Execute automation - Native button) & Object Id (the Id of the straight table: "Update sales stage").
3. "Do Query" - Add MySQL connection.
4. "Update Variable" - Use "do lookup" to configure App Id (Writeback demos) & Variable Id (last_update).
5. "Do Reload" - Use "do lookup" to configure App Id (Writeback demos).
6. "Save App" - Writeback demos.

If a Qlik Sense document uses Section Access to restrict user access, the following error may be seen during data load:

Access was denied after reload. Check that the user that reloads the script is included in the section access part of the script.

Environment

• Qlik Sense Enterprise on Windows
• Qlik Cloud Analytics

Resolution

Multiple root causes and matching solutions exist: 

The user loading the script does not have ADMIN permission in Section Access

Verify that the user executing the script has ADMIN access in the Section Access table.

Field data is not upper-case

All field data (such as userID, email) must be written in upper-case.

Column name for Section Access (ACCESS, USER.EMAIL, USERID, etc) is wrong

Make sure the column names are correct. If these are not matched, use an "as" prefix to adjust it.

Example: ACCESS, USERID, USER.EMAIL

LOAD ACCESS, 
  EMAIL as USER.EMAIL, 
  REDUCTION, 
  OMITGROUP; 

SELECT ACCESS, 
  EMAIL, 
  REDUCTION, 
  OMITGROUP

Cause

• The user loading the script does not have ADMIN permission in Section Access
• Field data is not upper-case
• Column name for Section Access (ACCESS, USER.EMAIL, USERID, etc) is wrong

Related Content 

• Managing data security with Section Access (Qlik Sense on-premise)
• Managing data security with Section Access (Qlik Cloud Analytics)

The conclusions in this article were reached in collaboration with cjgorrin from the European Commission's Joint Research Centre Qlik Sense team.

With Qlik Sense's new feature, Chart-level scripts, the Replace prefix replaces all values ​​in the HC1 table with a calculated value defined by the script.

Based on the Qlik Sense online documentation, using the attached CHART LEVEL SCRIPT_REPLACE RESIDENT load.qvf, we would expect the table to display the correct result regardless if an as (alias statement) is used or not.

Example One: Even if "as" is not used in the REPLACE statement, the error Load statement with star ('*') not supported in hypercube is displayed.

REPLACE LOAD 
  MyDim1, 
  MyDim2, 
  MyMeasure1, 
  MyMeasure2
RESIDENT HC1;

Example Two: If "as" is used in the REPLACE statement, no error is displayed but all rows are loaded with the same values. The values should remain unchanged.

REPLACE LOAD 
  MyDim1 as MyDim1, 
  MyDim2 as MyDim2, 
  MyMeasure1 as MyMeasure1, 
  MyMeasure2 as MyMeasure2 
RESIDENT HC1;

Resolution

This issue is caused by QB-27902, which will be resolved in an upcoming release of Qlik Sense Enterprise on Windows. Monitor the Release Notes for details.

Cause

REPLACE LOAD when used in a dynamic chart-level script is using only one row for the source data regardless of the actual number of source rows. It also incorrectly added rows to the chart.

Internal Investigation ID(s)

QB-27902

Environment

• Qlik Sense Enterprise on Windows May 2024

Loading a data file from OneDrive may fail with the following error:

Cannot open the following file: 'Failed on attempt 1 to GET. (unauthenticated, Unauthenticated). Check to confirm that the file is available and that you have permission to access it.

Not all users are affected.

Resolution

This is caused by QB-26980. This defect was resolved in Qlik Cloud during a September update.

If you encounter the problem in Qlik Sense Enterprise on-premise, upgrade to the the Qlik Sense Enterprise on Windows November 2024 release or any later version.

Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes with the ID QB-26980 for reference.

Cause

This involves a request to a pre-authenticated download URL and uses the Range header: Partial range downloads 

The Unauthenticated error is explained as The caller is not authenticated. For more information, see Detailed error codes (learn.microsoft.com).

Environment

• Qlik Sense Enterprise on Windows

Adding alternative measures or dimensions to a chart is expected to immediately update the chart. However, Qlik Sense May 2024 requires a page refresh before any changes are reflected correctly.

Earlier versions of Qlik Sense are not affected.

Resolution

This is caused by QB-26786. 

Workaround:

Refresh the page.

Fix Version:

Upgrade to Qlik Sense Enterprise on Windows November 2024 or any later versions.

Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes, or contact support with the ID QB-26786 for reference.

Environment

• Qlik Sense Enterprise on Windows May 2024, all patches

In this example, we load data from an Excel file hosted on SharePoint 365 using the Qlik Office 365 Sharepoint connector.

Environment:

For our example, we are using Qlik Sense Enterprise on Windows and the installed Qlik Web Connector for Office 365 Sharepoint. For more information on the Office 365 Sharepoint Qlik Web Connectors and for installation instructions, see: Office 365 Sharepoint and Installation Web Connectors.

Step by Step Instructions (as seen in the video)

Links provided in these examples are example links, not real links. 

1. Using a supported web browser, open up the Qlik Web Connectors Console
   YourWebConnectorServer:5555/web
2. Locate and click the Qlik Office 365 Sharepoint Connector
3. Select the CanAuthenticate table in the available Tables list on the left.
4. Click Parameters
5. Copy your Sharepoint base URL (where the file is located) into the Base URL field
   https://<yourO365TenantID>.sharepoint.com
6. Click Authenticate
7. This will open a new browser window with your Authentication Code. Copy the code to clipboard. 
8. Return to the previous browser window and paste the code into the Authentication Code field. Click Save.
9. Now click Save Inputs & Run Table
   A confirmation will be shown in the Data Preview tab reading true in the authenticated row.
10. Locate the ListFolders table in the available Tables list on the left.
11. Click Parameters 
12.  Provide the Base URL and Sub Site Path
    
    • Base URL: https://<yourO365TenantID>.sharepoint.com
    • Sub site Path: /sites/<yoursubsiteDirectoryPath>
13. Click Save Inputs and Run Table
14. In the now available list, locate the directory your file is located in.
15. Copy the path and paste it into the Folder field.
16. /sites/<yoursubsiteDirectoryPath>/Shared Documents/Functional Area - Development
17. Repeat this step if needed to continue listing nested folders until you locate the folder storing the file. 
18. Click Save Inputs and Run Table
19. Copy the folder ServerRelativeUrl
20. Locate the ListFiles table in the available Tables list on the left. This will allow us to identify the ID of the Excel file.
21. Click Parameters 
22. Paste the ServerRelativeUrl into the Folder field
23. Click Save Inputs and Run Table
24. The Data Preview tab will now show us the UniqueId of the xslx document you are interested in. In our example: cf079b74-1bc8-4a5a-971d-07321081a6ac
25. Copy the ID
26. Go back and choose the GetFile table
27.  The Sub Site path should be the subsite that you have previously used
28. Paste the UniqueId into the UniqueId For File field.
29. Click Save Inputs and Run Table
30. The Connector will now attempt to preview the data
31. Click the Qlik Sense (Standard Mode) tab
32. Copy the URL provided:
    http://localhost:5555/data?connectorID=Office365Connector&table=GetFile&subSite=%2fsites%2f<yoursubsiteDirectoryPath>&fileId=cf079b74-1bc8-4a5a-971d-07321081a6ac&appID=
33. Go to your app in Qlik Sense
34. Create a connection to a web file using that URL previously copied.
35. Reload the data to your Sense app

The conclusions in this article were reached in collaboration with cjgorrin from the European Commission's Joint Research Centre Qlik Sense team.

With Qlik Sense's new feature, Chart-level scripts, Add prefix is used with LOAD to append values to the HC1 table, representing the hypercube computed by the Qlik associative engine.

Based on this documentation and using the attached CHART LEVEL SCRIPT_ADD RESIDENT Load.qvf,  we would expect the table to have 12 entries (6 original and 6 new)

Example: as the hypercube already has 6 entries, we would expect 6 new entries to be added when using Add prefix. 

ADD LOAD 
  MyDim1 as MyDim1, 
  MyDim2 as MyDim2, 
  MyMeasure1*100 as MyMeasure1, 
  MyMeasure2*1000 as MyMeasure2 
RESIDENT HC1

The result only shows 6 rows, with only one of them being modified:

Resolution

This is working as designed. 

ADD LOAD RESIDENT will try to merge duplicate rows and the test cases expect this behavior. 

Workaround

To workaround this specific user case, add a blank space to one of the dimensions, as shown below:

ADD LOAD 
 MyDim1&' ' as MyDim1, 
 MyDim2 as MyDim2, 
 MyMeasure1*100 as MyMeasure1, 
 MyMeasure2*1000 as MyMeasure2 
RESIDENT HC1;"

Internal Investigation ID(s):

QB-27903

Environment

• Qlik Sense May 2024 and above
• Qlik Sense Cloud

The conclusions in this article were reached in collaboration with cjgorrin from the European Commission's Joint Research Centre Qlik Sense team.

Based on Qlik Sense online documentation, a PUT statement can be used to access columns, rows i.e. to set a numeric value to the hypercube.

However, using a Dimension name in a PUT statement, the following error is thrown:

Load statement could not find target column [MyDim1] in hypercube

Resolution

This is working as designed.

Put statements are not allowed to manipulate dimensions. The Qlik Sense online help will be updated to reflect this. 

Internal Investigation ID(s):

QB-27904

Environment

• Qlik Sense May 2024 and above
• Qlik Sense Cloud